5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.ENV GET PATH NAME


This subroutine returns the path name of the requested Appx file.

Usage:

Description:

This subroutine returns the path name of the requested Appx file. The first three parameters are required, if any are missing the subroutine will CANCEL. The remaining parameters are optional, depending on the type of file (see below).

<file_path> returns the path and file name of the requested file (Required). This must be PASSed with Share "Y" to return the value. Note that this will not include the '.dat' extension

<app_id> is the application id of the file you are interested in (Required).

<file_name> is the Data Dictionary name of the file you are interested in (Required).

<error_msg> will contain any additional error information (optional).

<database> is the name of the database that contains the file you are interested in. If not PASSed, it will default to the current database.

<version> is the version that contains the file you are interested in. If not PASSed, it will default to the version used by <database>, unless you are checking a Design File (see below).

This will only work for permanent disk based files. You cannot use this on Appx/Net files, or files stored in a RDBMS.

There are 3 types of files you can inquire on. Each type has it's own requirements for the parameters that must be passed:

Normal Data Files

  • <app_id> must be supplied
  • <database> is optional and will default to the current database
  • <version> is optional and will default to the start up version of the specified database

System Administration Files

  • <app_id> can be blank, the contents will be ignored.
  • <database> must be 0SA
  • <version> can be blank, the contents will be ignored.

Application Design Files

  • <app_id> must be filled in.
  • <database> must be 0AD
  • <version> must be filled in.

If the field you passed in <file_path> is too short to contain the data, --- .ENV GET PATH NAME will be set to "Data was truncated".


 

Application Design Manual                                         "Powered by Appx Software"

1235

©2006 By APPX Software, Inc. All Rights Reserved